Method for reconfiguring data radio bearer and user equipment

ABSTRACT

Provided is a method executed by user equipment, including: receiving a radio resource control (RRC) connection reconfiguration message; determining whether the received RRCConnectionReconfiguration message contains indication information, the indication information indicating user equipment (UE) to reconfigure a first type of data radio bearer (DRB) into a second type of DRB that is different from the first type of DRB; and in a case where the received RRCConnectionReconfiguration message contains the indication information, reconfiguring the UE according to the RRCConnectionReconfiguration message, wherein the first type of DRB includes a main cell group (MCG) DRB or a wireless local area network (WLN) non-split DRB, and the second type of DRB includes an MCG DRB, a WLN split DRB or a WLN non-split DRB. Corresponding user equipment is also provided.

TECHNICAL FIELD

The present invention relates to mobile communication, in particular toa method for reconfiguring data radio bearer and user equipment.

BACKGROUND

Interoperability and integration of the Long Term Evolution (LTE) systemof 3GPP and the Wireless Local Area Network (WLAN) at the core networklevel have been defined in the 3GPP standardization documents. 3GPP LTERelease 12 has studied the interoperability and integration of LTE andWLAN at the RAN level (see 3GPP TR37.834).

At the 3GPP TSG RAN #67 meeting, a research proposal was approved toenhance the integration and interoperability of LTE-WLAN at the RANlevel in 3GPP LTE Release 13 (see 3GPP Proposal RP-150510). Research onenhancing integration and interoperability of LTE-WLAN at the RAN levelincludes: enhancing integration of LTE-WLAN at the RAN level andenhancing the interoperability of LTE-WLAN at the RAN level. Theintegration of LTE-WLAN at the RAN level means that user equipment inthe RRC connection state is configured to utilize the radio resources,provided by both LTE and WLAN, all the while not affecting the existingstandards on the MAC layer of WLAN. Enhancing integration of LTE-WLAN atthe RAN level is based on dual-connection options, i.e., 2C and 3C, asdefined by 3GPP LTE Release 12.

The options 2C and 3C illustrated in FIGS. 1 and 2 contain two logicalnodes: main base station (MeNB) and WLN logical node. The MeNB refers toa base station that supports the integration and interoperability ofLTE-WLN and is responsible for maintaining the RRM (Radio ResourceManagement) measurement configuration of user equipment and requestingthe WLN to provide additional resources for the user equipment based onthe received measurement report or traffic status or bearer type, etc.The WLN provides a data transmission service for the user equipment orrejects the request due to insufficient resources after receiving therequest from the MeNB. The WLN refers to a logical node having functionsof receiving user data from the MeNB and forwarding the data to the userequipment by using the radio resources provided by the WLAN.

The option 2C illustrated in FIG. 1 has the following characteristics:(1) the MeNB communicates with a service gateway through an S1-Uinterface; (2) a data radio bearer (DRB) is not split in the MeNB; (3) aPacket Data Convergence Protocol (PDCP) entity at the MeNB encapsulatesthe PDCP SDU from the service gateway into a format required by areceiving entity (known as an adaptation entity or WLN entity) of theWLN and sends it to the adaptation entity. The adaptation entityencapsulates the data received from the PDCP entity of the MeNB asrequired and then transmits it to the user equipment (UE) via the WLANradio resources. Herein, the UE may be a user terminal, a user node, amobile terminal, or a tablet computer. In the following description, thedata radio bearer with characteristics of the option 2C is referred toas a WLN non-split data radio bearer (WLN non-split DRB).

The option 3C illustrated in FIG. 2 has the following characteristics:(1) the MeNB communicates with a service gateway through an S1-Uinterface; (2) a data radio bearer is split in the MeNB; (3) for a splitdata radio bearer, there is a corresponding radio link control (RLC)entity in the MeNB. The PDCP entity located at the MeNB encapsulates thePDCP SDU from the service gateway into a PDCP PDU and sends a portion ofthe encapsulated PDCP PDU to the UE through the RLC entity, the MACentity, and the physical layer of the MeNB. The remaining PDCP PDU isfurther encapsulated as required and sent to the adaptation entity ofthe WLN, and to the UE via radio resources provided by the WLAN. In thefollowing description of the present invention, a data radio bearerhaving the characteristics of the option 3C is referred to as WLN splitdata radio bearer (WLN split DRB).

The master cell group (MCG) cited in the present invention refers to agroup of serving cells of UE, and the group of serving cells contains aprimary cell (PCell) and 0 or more secondary cells (SCell). Based on thearchitecture of options 2C and 3C, in a system of LTE-WLAN integrationand interoperation, in a case where user data transmitted by a DRB istransmitted only by using the MCG (i.e., the user data transmitted by aDRB is transmitted to UE via the PDCP entity, the RLC Entity, MACentity, and physical layer (PHY) of the MCG), then the DRB is called themaster cell group DRB (MCG DRB). In a case where the user datatransmitted by a DRB is transmitted simultaneously using the radioresources of the MCG and the radio resources of the WLAN (i.e., a partof the user data transmitted by a DRB is transmitted to UE via the PDCPentity, the RLC entity, the MAC entity, and the physical layer PHY ofthe MCG, and the other part of the user data is transmitted to the UEvia the PDCP entity of the MCG and the WLAN), then the DRB is called WLNsplit DRB (WLN split DRB). In a case where the user data transmitted bya DRB is encapsulated by the PDCP entity of the MCG and transmitted byusing the radio resources provided by the WLAN, this DRB is called a WLNnon-split data DRB (WLN non-split DRB). In other words, the user data ofthe WLN non-split DRB is not transmitted by the radio resources providedby the LTE, but rather is encapsulated by using the PDCP entity of theMCG, sent to the WLN, and then transmitted to the user equipment throughthe WLAN radio resources. In the present invention, the WLN split DRBand the WLN non-split DRB are collectively referred to as WLN DRB. Thatis, the WLN DRB mentioned in the present invention may indicate either aWLN split DRB or a WLN non-split DRB.

In a LTE-WLAN integrated system, it is necessary to dynamically performDRB reconfiguration between the MeNB and the WLN, based on the availableradio resources of the MeNB and the WLN. For example, when the MeNBcannot provide sufficient radio resources for the UE, the WLN may berequested to provide radio resources for the UE, i.e., the MCG DRB isreconfigured as a WLN split DRB or WLN non-split DRB. When the MeNB andthe WLN are simultaneously serving the UE (i.e., based on thearchitecture of the option 3C), in a case where the MeNB has more radioresources available to the UE for a period of time but the WLN does nothave sufficient radio resources available to the UE, the MeNB mayreconfigure the DRB to the MeNB. In other words, reconfiguring the WLNsplit DRB as an MCG DRB, and in a case where the MeNB has no radioresources available to the UE for a period of time, but the WLN canprovide more radio resources for the UE, the MeNB may reconfigure theDRB to the WLN, that is, the WLN split DRB is reconfigured as a WLNnon-split DRB. When the WLN provides radio resources for UE alone tocarry out data transmission after the data is encapsulated by the PDCPentity of the MeNB (i.e., an architecture based on the option 2C), in acase where the MeNB has more radio resources available to the UE for aperiod of time or the WLN does not have sufficient radio resourcesavailable to the UE, the MeNB may reconfigure the DRB to the MeNB Inother words, reconfiguring the WLN split DRB as an MCG DRB, and in acase where the MeNB can provide a portion of radio resources for the UEfor a period of time, in this case, the WLN non-split DRB isreconfigured as a WLN split DRB.

SUMMARY

It is an object of the present invention to solve the problem of radiobearer reconfiguration between a MeNB and a WLN.

According to one aspect of the present invention, there is provided amethod executed by user equipment, including: receiving a radio resourcecontrol (RRC) connection reconfiguration message; determining whetherthe received RRCConnectionReconfiguration message contains indicationinformation, the indication information indicating user equipment (UE)to reconfigure a first type of data radio bearer (DRB) into a secondtype of DRB that is different from the first type of DRB; and in a casewhere the received RRCConnectionReconfiguration message includes theindication information, reconfiguring the UE according to theRRCConnectionReconfiguration message, wherein the first type of DRBincludes a main cell group (MCG) DRB or a wireless local area network(WLAN) non-split DRB, and the second type of DRB includes an MCG DRB, aWLN split DRB or a WLN non-split DRB.

In one embodiment, the first type of DRB is an MCG DRB, the second typeof DRB is a WLN split DRB, and reconfiguring the UE according to theRRCConnectionReconfiguration message includes: reconfiguring an adaptionentity according to configuration information contained in theRRCConnectionReconfiguration message and related to the adaption entity;reconfiguring a PDCP (Packet Data Convergence Protocol) entity in a casewhere the RRCConnectionReconfiguration message contains configurationinformation related to the PDCP entity; releasing an MCG RLC (Radio LinkControl) entity and an MCG DTCH (dedicated channel) logical channel.

In one embodiment, the first type of DRB is an MCG DRB, the second typeof DRB is a WLN split DRB, and reconfiguring the UE according to theRRCConnectionReconfiguration message includes: establishing an adaptionentity according to configuration information contained in theRRCConnectionReconfiguration message and related to the adaption entity;reconfiguring a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; releasing an MCG RLC entity and an MCG DTCHlogical channel.

In one embodiment, the first type of DRB is a WLN split DRB, the secondtype of DRB is an MCG DRB, and reconfiguring the UE according to theRRCConnectionReconfiguration message includes: reconfiguring a PDCPentity in a case where the RRCConnectionReconfiguration message containsconfiguration information related to the PDCP entity; reconfiguring anMCG RLC entity and an MCG DTCH logical channel in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the RLC entity and the MCG DTCH logical channel; andreconfiguring an adaption entity according to configuration informationcontained in the RRCConnectionReconfiguration message and related to theadaption entity.

In one embodiment, the first type of DRB is a WLN non-split DRB, thesecond type of DRB is an MCG DRB, and reconfiguring the UE according tothe RRCConnectionReconfiguration message includes: reconfiguring a PDCPentity in a case where the RRCConnectionReconfiguration message containsconfiguration information related to the PDCP entity; establishing anMCG RLC entity and MCG DTCH logical channel in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the RLC entity and the MCG DTCH logical channel; andreleasing an adaption entity.

In one embodiment, the first type of DRB is a WLN non-split DRB, thesecond type of DRB is a WLN split DRB, and reconfiguring the UEaccording to the RRCConnectionReconfiguration message includes:establishing an MCG RLC entity and MCG DTCH logical channel according tothe configuration information contained in theRRCConnectionReconfiguration message and related to the MCG RLC entityand the MCG DTCH logical channel; reconfiguring a PDCP entity in a casewhere the RRCConnectionReconfiguration message contains configurationinformation related to the PDCP entity; and reconfiguring an adaptionentity in a case where the RRCConnectionReconfiguration message containsconfiguration information related to the adaption entity.

In one embodiment, the method further includes: re-establishing the PDCPentity.

In one embodiment, whether to re-establish the PDCP is ascertained bytransmitting an RRC signaling to the UE.

In one embodiment, the indication information contains adrb-TypeChangWLN carried in drb-ToAddModList information element and adrb-TypeWLN information element carried in a drb-ToAddModListWLN. Thedrb-ToAddModList information element is a group of DRBs in need ofaddition or modification; the drb-TypeChangWLN information element isused for indicating whether to reconfigure a WLN split DRB or a WLNnon-split DRB as an MCG DRB. The drb-ToAddModListWLN information elementis a group of WLN DRBs in need of addition or modification. Thedrb-TypeWLN information element represents the Type of correspondingDRB. Preferably, according to the value of the drb-TypeWLN informationelement and whether the DRB corresponding to the drb-TypeWLN informationelement is contained in the drb-ToAddModList information element and thedrb-ToAddModListWLN information element, it is possible to determinewhether to reconfigure an MCG DRB as a WLN non-split DRB, a WLNnon-split DRB as an MCG DRB, or a WLN non-split DRB as a WLN split DRB.

According to one aspect of the present invention, there is provided userequipment, including: a receiving unit, configured to receive a radioresource control (RRC) connection reconfiguration message; a determiningunit, configured to determine whether the receivedRRCConnectionReconfiguration message contains indication information,the indication information indicating user equipment (UE) to reconfigurea first type of data radio bearer (DRB) into a second type of DRB thatis different from the first type of DRB; and a reconfiguring unit,configured to reconfigure the UE according to theRRCConnectionReconfiguration message in a case where the receivedRRCConnectionReconfiguration message contains the indicationinformation, wherein the first type of DRB includes a main cell group(MCG) DRB or a wireless local area network (WLN) non-split DRB, and thesecond type of DRB includes an MCG DRB, a WLN split DRB or a WLNnon-split DRB.

In one embodiment, the first type of DRB is an MCG DRB, the second typeof DRB is a WLN non-split DRB, and the reconfiguring unit is configuredto reconfigure an adaption entity according to configuration informationcontained in the RRCConnectionReconfiguration message and related to theadaption entity; reconfigure a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; and release an MCG RLC entity and an MCGDTCH logical channel.

In one embodiment, the first type of DRB is an MCG DRB, the second typeof DRB is a WLN non-split DRB, and the reconfiguring unit is configuredto establish an adaption entity according to configuration informationcontained in the RRCConnectionReconfiguration message and related to theadaption entity; reconfigure a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; and release an MCG RLC entity and an MCGDTCH logical channel.

In one embodiment, the first type of DRB is a WLN non-split DRB, thesecond type of DRB is an MCG DRB, and the reconfiguring unit isconfigured to reconfigure a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; establish an MCG RLC entity and an MCG DTCHlogical channel in a case where the RRCConnectionReconfiguration messagecontains configuration information related to the RLC entity and the MCGDTCH logical channel; and reconfigure an adaption entity in a case wherethe RRCConnectionReconfiguration message contains configurationinformation related to the adaption entity.

In one embodiment, the first type of DRB is a WLN non-split DRB, thesecond type of DRB is an MCG DRB, and the reconfiguring unit isconfigured to reconfigure a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; establish an MCG RLC entity and an MCG DTCHlogical channel in a case where the RRCConnectionReconfiguration messagecontains configuration information related to the RLC entity and the MCGDTCH logical channel; and release an adaption entity.

In one embodiment, the first type of DRB is a WLN non-split DRB, thesecond type of DRB is an MCG DRB, and the reconfiguring unit isconfigured to establish an MCG RLC entity and an MCG DTCH logicalchannel according to configuration information contained in theRRCConnectionReconfiguration message and related to the adaption entity;reconfiguring a PDCP entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the PDCP entity; releasing an MCG RLC entity and an MCG DTCHlogical channel; and reconfigure an adaption entity in a case where theRRCConnectionReconfiguration message contains configuration informationrelated to the adaption entity.

In one embodiment, the UE further includes: a re-establishing unit,configured to re-establish the PDCP entity.

In one embodiment, whether to re-establish the PDCP is ascertained bytransmitting an RRC signaling to the UE.

In one embodiment, the indication information contains adrb-TypeChangWLN information element carried in drb-ToAddModListinformation element and a drb-TypeWLN information element carried in adrb-ToAddModListWLN information element. The drb-ToAddModListinformation element is a group of DRBs in need of addition ormodification; the drb-TypeChangWLN information element is used forindicating whether to reconfigure a WLN split DRB or a WLN non-split DRBas an MCG DRB. The drb-ToAddModListWLN information element is a group ofWLN DRBs in need of addition or modification. The drb-TypeWLNinformation element represents the Type of a corresponding DRB.Preferably, according to the value of the drb-TypeWLN informationelement and whether the DRB corresponding to the drb-TypeWLN informationelement is contained in the drb-ToAddModList information element and thedrb-ToAddModListWLN information element, it is possible to determinewhether to reconfigure an MCG DRB as a WLN non-split DRB or reconfigurea WLN non-split DRB as an MCG DRB or reconfigure a WLN non-split DRB asa WLN split DRB.

DESCRIPTION OF THE DRAWINGS

The features described above and other features of the present inventionwill become more apparent from the following detailed description inconjunction with the accompanying drawings, wherein

FIG. 1 is a schematic diagram of the option 2C of the LET-WLNintegration and interoperability deployment;

FIG. 2 is a schematic diagram of the option 3C of the LET-WLNintegration and interoperability deployment;

FIG. 3 is a flow chart of a method for reconfiguring an MCG DRB as a WLNsplit DRB, provided by an embodiment of the present invention;

FIG. 4 is a flow chart of a method for reconfiguring an MCG DRB as a WLNnon-split DRB, provided by an embodiment of the present invention;

FIG. 5 is a flow chart of a method for reconfiguring a WLN split DRB asan MCG DRB, provided by an embodiment of the present invention;

FIG. 6 is a flow chart of a method for reconfiguring a WLN split DRB asa WLN non-split DRB, provided by an embodiment of the present invention;

FIG. 7 is a flow chart of a method for reconfiguring a WLN non-split DRBas an MCG DRB, provided by an embodiment of the present invention;

FIG. 8 is a flow chart of a method for reconfiguring a WLN non-split DRBas a WLN split DRB, provided by an embodiment of the present invention;

FIG. 9 is a flow chart of a method in which theRRCConnectionReconfiguration message carries indication information forindicating the UE to reconfigure a type of DRB into another type of DRB,provided by an embodiment of the present invention;

FIG. 10 is a flow chart of a method in which theRRCConnectionReconfiguration message carries indication information forindicating the UE to reconfigure a type of DRB into another type of DRB,provided by an embodiment of the present invention; and

FIG. 11 is a block diagram of user equipment according to an embodimentof the present invention.

DESCRIPTION OF THE EMBODIMENTS

The principle and implementation of the present invention will becomeapparent from the following description on specific embodiments of thepresent invention in conjunction with the accompanying drawings. Notethat the present invention shall not be limited to the specificembodiments described below. In addition, for simplicity, a detaileddescription on the known art not directly related to the presentinvention is omitted to prevent confusion in the understanding of thepresent invention.

In the following description, an LTE Rel-13 mobile communication systemand its later evolved releases are used as exemplary applicationenvironments to set forth embodiments of the present invention indetail. Note, however, that the present invention is not limited to thefollowing embodiments and may be applicable to more other wirelesscommunication systems, such as a future 5G cellular communicationsystem. In addition, although the implementation examples of thetechnical solution of the present invention is described with respect tothe case where the MeNB cooperates with one WLN to provide acommunication service for the UE, a person skilled in the art would beconceivable of that the technical solution of the present inventionlikewise is applicable to the cases where the MeNB cooperates with morethan one WLN to provide a communication service for the UE.

In the LTE system, the UE carries out the processes of adding(establishing) and reconfiguring a DRB according to a receivedRRCConnectionReconfiguration message. The RRCConnectionReconfigurationmessage is mainly used for establishing/modifying/releasing radiobearers (RBs) and executing switching, establishing/modifying/releasingmeasurement and the like. The RBs include signaling radio bearers (SRBs)and data radio bearers (DRBs) The data radio bearers (DRBs) include MCGDRBs, split DRBs (bearers for dual connection option 3C described in3GPP Release 12), SCG DRBs (bearers for dual connection option 1Adescribed in 3GPP Release 12), and bears for the transmission of userdata, such as WLN split DRBs and WLN non-split DRBs.

In the following, the meanings of parameters contained in theRRCConnectionReconfiguration message cited herein are described.Furthermore, in a case where a parameter mentioned herein is the same asthat in 3GPP TS36.331 in denomination, the meaning and inclusionrelation between cells, represented by it, are the same as those in 3GPPTS36.331.

drb-ToAddModListWLN information element: a group of WLN DRBs in need ofaddition or modification;drb-ToAddModList information element a group of DRBs in need of additionor modification; Adaptation-Config information element: containingconfigurable parameters corresponding to an adaption entity used forconfiguring WLN DRB;pdcp-Config information element: containing configurable PDCP parametersof DRB; drb-Identity information element: DRB ID;rlc-Config information element: containing configuration information ofan RLC entity corresponding to SRB and DRB;logicalChannelIdentity information element: logical channel ID; and:logicalChannelConfig information element: containing parameters forconfiguring a logical channel.

FIG. 3 illustrates a flow chart of a method for reconfiguring an MCG DRBas a WLN split DRB. The method illustrated in FIG. 3 includes thefollowing steps:

Step 301: UE receives the RRCConnectionReconfiguration message anddetermines whether the message carries indication information used forindicating UE to reconfigure an MCG DRB as a WLN split DRB; in a casewhere the message carries the indication information, step 302 a or step302 b is executed according to the correspondence between the WLN DRBand an adaptation entity; otherwise, the process is ended.

In a case where there is a many-to-one mapping relationship between theWLN DRB and the adaptation entity, the process goes to step 302 a; in acase where there is a one-to-one mapping relationship between the WLNDRB and the adaptation entity, the process goes to step 302 b.

Step 302 a: The UE reconfigures the adaptation entity according to theAdaptation-Config information element carried in drb-ToAddModListWLN.

Alternatively, an adaptation entity is to be established in a case wherethere is no adaptation entity in the WLN, i.e., the WLN split DRBreconfigured by the MCG DRB is the first WLN DRB of the adaptationentity.

Step 302 b: The user establishes an adaptation entity based on theAdaptation-Config information element carried in drb-ToAddModListWLN.

Step 303: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 304: In a case where the drb-ToAddModList carries the rlc-Configinformation element, the logicalChannelIdentity information element, andthe logicalChannelConfig information element, the MCG RLC entity and theMCG DTCH logical channel are reconfigured according to the rlc-Configinformation element, the logicalChannelIdentity information element, andthe logicalChannelConfig information element.

Note that the execution sequence of step 302 a (or 302 b), step 303, andstep 304 may be arbitrarily changed.

Alternatively, when the UE reconfigures the MCG DRB as the WLN splitDRB, the UE re-establishes the PDCP entity and the RLC entity andtransmits a PDCP status report. Alternatively, the UE may be configuredaccording to an RRC signaling whether to re-establish the PDCP entityand the RLC entity and transmit the PDCP status report when the MCG DRBis reconfigured as WLN split DRB.

FIG. 4 illustrates a flow chart of a method for reconfiguring an MCG DRBas a WLN non-split DRB. The method illustrated in FIG. 4 includes thefollowing steps:

Step 401: UE receives the RRCConnectionReconfiguration message anddetermines whether the message carries an indication information usedfor indicating UE to reconfigure an MCG DRB as a WLN non-split DRB; in acase where the message carries the indication information, step 402 a orstep 402 b is executed according to the correspondence between the WLNDRB and an adaptation entity; otherwise, the process is ended.

In a case where there is a many-to-one mapping relationship between theWLN DRB and the adaptation entity, the process goes to step 402 a; in acase where there is a one-to-one mapping relationship between the WLNDRB and the adaptation entity, the process goes to step 402 b.

Step 402 a: The UE reconfigures the adaptation entity according to theAdaptation-Config information element carried in drb-ToAddModListWLN.

Alternatively, an adaptation entity is to be established in a case wherethere is no adaptation entity in the WLN, i.e., the WLN non-split DRBreconfigured by the MCG DRB is the first WLN DRB of the adaptationentity.

Step 402 b: The UE establishes an adaptation entity based on theAdaptation-Config information element carried in drb-ToAddModListWLN.

Step 403: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 404: The MCG RLC entity and the MCG DTCH logical channel arereleased.

Note that the execution sequence of step 402 a (or 402 b), step 403, andstep 404 may be arbitrarily changed.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the MCG DRB is reconfigured as the WLN non-splitDRB. Alternatively, the UE may be configured according to an RRCsignaling whether to re-establish the PDCP entity and transmit the PDCPstatus report when the MCG DRB is reconfigured as the WLN split DRB.

FIG. 5 illustrates a flow chart of a method for reconfiguring a WLNsplit DRB as an MCG DRB. The method illustrated in FIG. 5 includes thefollowing steps:

Step 501: UE receives the RRCConnectionReconfiguration message anddetermines whether the message carries an indication information usedfor indicating UE to reconfigure a WLN split DRB as an MCG DRB; in acase where the message carries the indication information, step 502 a orstep 502 b is executed according to the correspondence between the WLNDRB and an adaptation entity; otherwise, the process is ended.

In a case where there is a many-to-one mapping relationship between theWLN DRB and the adaptation entity, the process goes to step 502 a; in acase where there is a one-to-one mapping relationship between the WLNDRB and the adaptation entity, the process goes to step 502 b.

Step 502 a: In a case where the Adaptation-Config information element iscarried in the drb-ToAddModListWLN, the adaption entity is reconfiguredaccording to the Adaptation-Config information element.

Alternatively, in a case where there is no other WLN DRB in theadaptation entity after the WLN split DRB is reconfigured as the MCGDRB, the adaptation entity is released.

Step 502 b: The adaptation entity is released, that is, the relevantinformation of the WLN split DRB which is reconfigured as the MCG DRB inthe WLN is released.

Step 503: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 504: In a case where the drb-ToAddModList carries the rlc-Configinformation element, the logicalChannelIdentity information element, andthe logicalChannelConfig information element, the MCG RLC entity and theMCG DTCH logical channel are reconfigured according to the rlc-Configinformation element, the logicalChannelIdentity information element, andthe logicalChannelConfig information element.

Note that the execution sequence of step 502 a (or 502 b), step 503, andstep 504 may be arbitrarily changed.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the WLN split DRB is reconfigured as the MCGDRB. Alternatively, the UE may be configured according to an RRCsignaling whether to re-establish the PDCP entity and transmit the PDCPstatus report when the MCG DRB is reconfigured as the WLN split DRB.

FIG. 6 illustrates a flow chart of a method for reconfiguring a WLNsplit DRB as a WLN non-split DRB. The method illustrated in FIG. 6includes the following steps:

Step 601: UE receives an RRCConnectionReconfiguration message anddetermines whether the message carries an indication information usedfor indicating the UE to reconfigure a WLN split DRB as a WLN non-splitDRB; in a case where the message carries the indication message, theprocess goes to step 602; otherwise, the process is ended.

Step 602 a: In a case where the Adaptation-Config information element iscarried in the drb-ToAddModListWLN, the adaption entity is reconfiguredaccording to the Adaptation-Config information element.

Step 603: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 604: The MCG RLC entity and the MCG DTCH logical channel arereleased.

Note that the execution sequence of step 602, step 603, and step 604 maybe arbitrarily changed.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the WLN split DRB is reconfigured as the WLNnon-split DRB. Alternatively, the UE may be configured according to anRRC signaling whether to re-establish the PDCP entity and transmit thePDCP status report when the MCG DRB is reconfigured as the WLN splitDRB.

FIG. 7 illustrates a flow chart of a method for reconfiguring a WLNnon-split DRB as an MCG DRB. The method illustrated in FIG. 7 includesthe following steps:

Step 701: UE receives the RRCConnectionReconfiguration message anddetermines whether the message carries an indication information usedfor indicating UE to reconfigure a WLN non-split DRB as an MCG DRB; in acase where the message carries the indication information, step 702 a orstep 702 b is executed according to the correspondence between the WLNDRB and an adaptation entity; otherwise, the process is ended.

In a case where there is a many-to-one mapping relationship between theWLN DRB and the adaptation entity, the process goes to step 702 a; in acase where there is a one-to-one mapping relationship between the WLNDRB and the adaptation entity, the process goes to step 702 b.

Step 702 a: In a case where the Adaptation-Config information element iscarried in the drb-ToAddModListWLN, the adaption entity is reconfiguredaccording to the Adaptation-Config information element.

Alternatively, in a case where there is no other WLN DRB in theadaptation entity after the WLN non-split DRB is reconfigured as the MCGDRB, the adaptation entity is released.

Step 702 b: The adaptation entity is released, that is, the relevantinformation of the WLN non-split DRB which is reconfigured as the MCGDRB in the WLN is released.

Step 703: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 704: The MCG RLC entity and the MCG DTCH logical channel areestablished according to the rlc-Config information element, thelogicalChannelIdentity information element, and the logicalChannelConfiginformation element, carried in the drb-ToAddModList.

Note that the execution sequence of step 702 a (or 702 b), step 703, andstep 704 may be arbitrarily changed.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the WLN non-split DRB is reconfigured as the MCGDRB. Alternatively, the UE may be configured according to an RRCsignaling whether to re-establish the PDCP entity and transmit the PDCPstatus report when the MCG DRB is reconfigured as the WLN split DRB.

FIG. 8 illustrates a flow chart of a method for reconfiguring a WLNnon-split DRB as a WLN split DRB. The method illustrated in FIG. 8includes the following steps:

Step 801: UE receives an RRCConnectionReconfiguration message anddetermines whether the message carries an indication information usedfor indicating the UE to reconfigure a WLN non-split DRB as a WLN splitDRB; in a case where the message carries the indication message, theprocess goes to step 802; otherwise, the process is ended.

Step 802: In a case where the Adaptation-Config information element iscarried in the drb-ToAddModListWLN, the adaption entity is reconfiguredaccording to the Adaptation-Config information element.

Step 803: In a case where the pdcp-Config information element is carriedin the drb-ToAddModList, the PDCP entity is reconfigured according tothe pdcp-Config information element.

Step 804: The MCG RLC entity and the MCG DTCH logical channel areestablished according to the rlc-Config information element, thelogicalChannelIdentity information element, and the logicalChannelConfiginformation element, carried in the drb-ToAddModList.

Note that the execution sequence of step 802 a (or 802 b), step 803, andstep 804 may be arbitrarily changed.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the WLN non-split DRB is reconfigured as the WLNsplit DRB. Alternatively, the UE may be configured according to an RRCsignaling whether to re-establish the PDCP entity and transmit the PDCPstatus report when the MCG DRB is reconfigured as the WLN split DRB.

FIG. 9 and FIG. 10 respectively illustrate flow charts of two methods inwhich the RRCConnectionReconfiguration message carries indicationinformation for indicating the UE to reconfigure a type of DRB intoanother type of DRB. The DRBs at least include WLN split DRB, WLNnon-split DRB, MCG DRB. In the method illustrated in FIGS. 9 and 10, theUE determines whether to reconfigure a certain type of DRB as anothertype of DRB, according to the drb-TypeChangeWLN information elementcarried in the drb-ToAddModList information element and the drb-TypeWLNinformation element carried in the drb-ToAddModListWLN informationelement. The drb-TypeChangWLN information element is used to indicatewhether to reconfigure a WLN DRB (including WLN split DRB, WLN non-splitDRB) as an MCG DRB. The drb-TypeWLN information element represents thetype of the corresponding DRB; according to the value of the drb-TypeWLNinformation element and whether the DRB corresponding to the drb-TypeWLNinformation element is contained in the drb-ToAddModList informationelement and the drb-ToAddModListWLN information element, the UEdetermines whether to reconfigure an MCG DRB as a WLN DRB, orreconfigure a WLN non-split DRB as a WLN split DRB, or reconfigure a WLNsplit DRB as a WLN non-split DRB. In the embodiment of the presentinvention, the value of the drb-TypeChangWLN information element isexpressed as: to MCG (indicating that WLN DRB is reconfigured as MCGDRB); the value of the drb-TypeWLN information element is expressed as:WLNsplit (indicating that the corresponding DRB is WLN split DRB) orWLNnon-split (indicating that the corresponding DRB is WLN non-splitDRB). Note that the valuing of the drb-TypeChangWLN information elementand the drb-TypeWLN information element include, but are not limited to,the above-described valuing mode.

The method illustrated in FIG. 9 includes the following steps (executedby UE):

Step 9001: UE receives an RRCConnectionReconfiguration message;

Step 9002: with respect to a DRB that has been configured in the UE (theDRB is identified as drb-Identity), the UE determines whether theRRCConnectionReconfiguration message contains a drb-ToAddModListinformation element, and whether the drb-identity is contained in thedrb-ToAddModList information element; If so, the process goes to step9003; otherwise, the process goes to step 9016;

Step 9003: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, and whetherthe drb-Identity is contained in the drb-ToAddModListWLN informationelement; If so, the process goes to step 9004; otherwise, the processgoes to step 9010;

Step 9004: the UE Determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is MCG DRB; If so, the processgoes to step 9005; otherwise, the process goes to step 9007;

Step 9005: the UE determines whether the drb-ToAddModListWLN informationelement contains the drb-TypeWLN information element associated with thedrb-Identity and whether the value of the drb-TypeWLN is WLNsplit; Ifso, the process goes to step 9006;

Step 9006: the UE reconfigures the MCG DRB as a WLN split DRB;

Step 9007: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is a WLN non-split DRB; If so,the process goes to step 9008;

Step 9008: the UE determines whether the drb-ToAddModListWLN informationelement contains the drb-TypeWLN information element associated with thedrb-Identity, and whether the value of the drb-TypeWLN is WLNsplit; Ifso, the process goes to step 9009;

Step 9009: the UE reconfigures the WLN non-split DRB as a WLN split DRB;

Step 9010: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is a WLN split DRB; If so, theprocess goes to step 9011; otherwise, the process goes to step 9013;

Step 9011: the UE determines whether the drb-ToAddModList informationelement contains a drb-TypeChangeWLN information element associated withthe drb-identity, and whether the value of the drb-TypeChangeWLN is toMCG; If so, the process goes to step 9012;

Step 9012: the UE reconfigures the WLN split DRB as an MCG DRB;

Step 9013: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is a WLN non-split DRB; If so,the process goes to step 9014;

Step 9014: the UE determines whether the drb-ToAddModList informationelement contains a drb-TypeChangeWLN information element associated withthe drb-Identity, and whether the value of the drb-TypeChangeWLN is toMCG? If so, the process goes to step 9015;

Step 9015: the UE reconfigures the WLN non-split DRB as an MCG DRB;

Step 9016: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, and whetherthe drb-identity is contained in the drb-ToAddModListWLN informationelement; If so, the process goes to step 9017; step 9017: the UEdetermines whether the DRB that has been configured in the UE and isidentified as drb-Identity is an MCG DRB. If so, the process goes tostep 9018; otherwise, the process goes to step 9020;

Step 9018: the UE determines whether the drb-ToAddModListWLN informationelement contains a drb-TypeWLN information element corresponding to thedrb-Identity, and whether the value of the drb-TypeWLN is WLNnon-split;If so, the process goes to step 9019;

Step 9019: the UE reconfigures the MCG DRB as a WLN non-split DRB;

Step 9020: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is a WLN split DRB; If so, theprocess goes to step 9021; step 9021: the UE determines whether adrb-TypeWLN information element corresponding to the drb-Identity iscontained in the drb-ToAddModListWLN information element, and whetherthe value of the drb-TypeWLN is WLNnon-split; If so, the process goes tostep 9022; and

Step 9022: the UE reconfigures the WLN split DRB as a WLN non-split DRB.

The method illustrated in FIG. 10 includes the following steps (executedby UE):

Step 1001: UE receives an RRCConnectionReconfiguration message;

Step 1002: the UE determines whether a DRB that has been configured inthe UE and is identified as drb-Identity is a WLN split DRB; If so, theprocess goes to step 1003; otherwise, the process goes to step 1008;

Step 1003: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModList information element, whether thedrb-ToAddModList information element contains the drb-identity, whetherthe drb-ToAddModList information element further contains adrb-TypeChangeWLN information element corresponding to the drb-identity,and whether the value of the drb-TypeChangeWLN is to MCG; If so, theprocess goes to step 1004; otherwise, the process goes to step 1005;

Step 1004: the UE reconfigures the WLN split DRB as an MCG DRB;

Step 1005: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, whether thedrb-ToAddModListWLN information element contains the drb-identity,whether the drb-ToAddModListWLN information element further contains adrb-TypeWLN information element corresponding to the drb-identity, andwhether the value of the drb-TypeWLN is WLNnon-split; If so, the processgoes to step 1006; otherwise, the process goes to step 1007;

Step 1006: the UE reconfigures the WLN split DRB as a WLN non-split DRB.

Step 1007: the UE reconfigures the MCG DRB as a WLN non-split DRB;

Step 1008: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is a WLN non-split DRB; If so,the process goes to step 1009; otherwise, the process goes to step 1014;

Step 1009: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModList information element, whether thedrb-ToAddModList information element contains the drb-identity, whetherthe drb-ToAddModList information element further contains adrb-TypeChangeWLN information element corresponding to the drb-identity,and whether the value of the drb-TypeChangeWLN is to MCG; If so, theprocess goes to step 1010; otherwise, the process goes to step 1011;

Step 1010: the UE reconfigures the WLN non-split DRB as an MCG DRB;

Step 1011: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, whether thedrb-ToAddModListWLN information element contains the drb-identity,whether the drb-ToAddModListWLN information element further contains adrb-TypeWLN information element corresponding to the drb-identity, andwhether the value of the drb-TypeWLN is WLNsplit; If so, the processgoes to step 1012; otherwise, the process goes to step 1013;

Step 1012: the UE reconfigures the WLN non-split DRB as a WLN split DRB.

Step 1013: the UE reconfigures the WLN split DRB as a WLN non-split DRB;

Step 1014: the UE determines whether the DRB that has been configured inthe UE and is identified as drb-Identity is MCG DRB. If so, the processgoes to step 1015; and

Step 1015: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, whether thedrb-ToAddModListWLN information element contains the drb-identity,whether the drb-ToAddModListWLN information element further contains adrb-TypeWLN information element corresponding to the drb-identity, andwhether the value of the drb-TypeWLN is WLNnon-split; If so, the processgoes to step 1016; otherwise, the process goes to step 1017;

Step 1016: the UE reconfigures the MCG DRB as a WLN non-split DRB;

Step 1017: the UE determines whether the RRCConnectionReconfigurationmessage contains a drb-ToAddModListWLN information element, whether thedrb-ToAddModListWLN information element contains the drb-identity,whether the drb-ToAddModListWLN information element further contains adrb-TypeWLN information element corresponding to the drb-identity, andwhether the value of the drb-TypeWLN is WLNsplit; If so, the processgoes to step 9018; and

Step 1018: the UE reconfigures the MCG DRB as a WLN split DRB;

Note that the process of reconfiguring the WLN split DRB as an MCG DRBin step 9012 and step 1004 may be carried out according to the procedureillustrated in FIG. 5. The process of reconfiguring the WLN split DRB asa WLN non-split DRB in step 9022 and step 1006 may be carried outaccording to the procedure illustrated in FIG. 6. The process ofreconfiguring the WLN non-split DRB as an MCG DRB in step 9015 and step1010 may be carried out according to the procedure illustrated in FIG.7. The process of reconfiguring the WLN non-split DRB as a WLN split DRBin step 9009 and step 1012 may be carried out according to the procedureillustrated in FIG. 8. The process of reconfiguring the MCG DRB as a WLNsplit DRB in step 9006 and step 1018 may be carried out according to theprocedure illustrated in FIG. 3. The process of reconfiguring the MCGDRB as a WLN non-split DRB in step 9019 and step 1016 may be carried outaccording to the procedure illustrated in FIG. 4.

According to an embodiment of the present invention, the user equipmentestablishing the WLN slit DRB includes the following process: in a casewhere there is a many-to-one mapping relationship between a WLN DRB andan adaptation entity, the adaptation entity is reconfigured according tothe Adaptation-Config information element carried in thedrb-ToAddModListWLN.

Alternatively, an adaptation entity is established in a case where thereis no adaptation entity in the WLN, i.e. the WLN split DRB that needs tobe established is the first WLN DRB of the adaptation entity. In a casewhere there is a one-to-one mapping relationship between a WLN DRB andan adaptation entity, the adaptation entity is established according tothe Adaptation-Config information element carried indrb-ToAddModListWLN. A PDCP entity is established according to thepdcp-Config information element carried in the drb-ToAddModList, and thePDCP entity is configured by using MCG security configurationinformation.

An MCG RLC entity and an MCG DTCH logical channel are establishedaccording to the rlc-Config information element, thelogicalChannelIdentity information element, and the logicalChannelConfiginformation element, carried in the drb-ToAddModList.

According to an embodiment of the present invention, the user equipmentestablishing the WLN non-split DRB includes the following process: in acase where there is a many-to-one mapping relationship between a WLN DRBand an adaptation entity, the adaptation entity is reconfiguredaccording to the Adaptation-Config information element carried in thedrb-ToAddModListWLN. Alternatively, an adaptation entity is establishedin a case where there is no adaptation entity in the WLN, i.e. the WLNsplit DRB that needs to be established is the first WLN DRB of theadaptation entity. In a case where there is a one-to-one mappingrelationship between a WLN DRB and an adaptation entity, the adaptationentity is established according to the Adaptation-Config informationelement carried in drb-ToAddModListWLN. A PDCP entity is establishedaccording to the pdcp-Config information element carried in thedrb-ToAddModList, and the PDCP entity is configured by using MCGsecurity configuration information. Alternatively, a PDCP entity isestablished according to the pdcp-Config information element carried inthe drb-ToAddModListWLN, and the PDCP entity is configured by using MCGsecurity configuration information.

According to an embodiment of the present invention, the user equipmentreconfiguring the WLN split DRB includes the following process: in acase where the Adaption-Config information element is carried in thedrb-ToAddModListWLN, the adaptation entity is reconfigured according tothe Adaptation-Config information element. In a case where thepdcp-Config information element is carried in the drb-ToAddModList, thePDCP entity is reconfigured according to the pdcp-Config informationelement. Alternatively, in a case where the pdcp-Config informationelement is carried in the drb-ToAddModListWLN, the PDCP entity isreconfigured according to the pdcp-Config information element. In a casewhere the drb-ToAddModList carries the rlc-Config information element,the logicalChannelIdentity information element, and thelogicalChannelConfig information element, the MCG RLC entity and the MCGDTCH logical channel are reconfigured according to the rlc-Configinformation element, the logicalChannelIdentity information element, andthe logicalChannelConfig information element. Alternatively, the UEre-establishes the PDCP entity and transmits a PDCP status report whenthe UE reconfigures a WLN split DRB. Alternatively, the UE may beconfigured according to an RRC signaling whether to re-establish thePDCP entity and transmit a PDCP status report when a WLN split DRB isreconfigured.

According to an embodiment of the present invention, the user equipmentreconfiguring the WLN split DRB includes the following process: in acase where the Adaption-Config information element is carried in thedrb-ToAddModListWLN, the adaptation entity is reconfigured according tothe Adaptation-Config information element. In a case where thepdcp-Config information element is carried in the drb-ToAddModList, thePDCP entity is reconfigured according to the pdcp-Config informationelement. Alternatively, in case where the pdcp-Config informationelement is carried in the drb-ToAddModListWLN, the PDCP entity isreconfigured according to the pdcp-Config information element.

Alternatively, the UE re-establishes the PDCP entity and transmits aPDCP status report when the UE reconfigures a WLN non-split DRB.Alternatively, the UE may be configured according to an RRC signalingwhether to re-establish the PDCP entity and transmit a PDCP statusreport when a WLN non-split DRB is reconfigured.

FIG. 11 is a block diagram of user equipment according to an embodimentof the present invention. As illustrated in FIG. 11, the UE 1100includes a receiving unit 1101, a determining unit 1102, and areconfiguring unit 1103. Alternatively, the UE 1100 may further includea re-establishing unit 1104.

The receiving unit 1101 may be configured to receive anRRCConnectionReconfiguration message.

The determining unit 1102 is configured to determine whether thereceived RRCConnectionReconfiguration message contains indicationinformation, the indication information indicating the UE to reconfigurethe first type of DRB as the second type of DRB that is different fromthe first type.

The reconfiguring unit 1103 is configured to reconfigure the UEaccording to the RRCConnectionReconfiguration message in a case wherethe received RRCConnectionReconfiguration message contains indicationinformation.

The re-establishing unit 1104 can be configured to re-establish a PDCPentity.

According to an embodiment of the present invention, the first type ofDRB may include an MCG DRB, a WLN split DRB or a WLN non-split DRB. Thesecond type of DRB may include an MCG DRB, a WLN split DRB, or a WLNnon-split DRB.

It will be appreciated by those skilled in the art that the UE 1100illustrated in FIG. 11 may be configured to perform the various methodsdescribed above with respect to FIGS. 3 to 10. For the sake of brevity,the description is not repeated herein.

It is to be understood that the above-described embodiments of thepresent invention may be implemented by software or by hardware or by acombination of both software and hardware. For example, the variouscomponents within the user equipment in the above embodiments may beimplemented by a variety of devices including, but not limited to,analog circuit devices, digital circuit devices, digital signalprocessing (DSP) circuits, programmable processors, application-specificintegrated circuits (ASICs), field programmable gate arrays (FPGAs),programmable logic devices (CPLDs), and the like.

In this application, the term “base station” refers to a mobilecommunication data and control switching center having a largetransmission power and a wide coverage area and including functions suchas resource allocation scheduling, data reception and transmission, andthe like.

The term “user equipment” refers to a user mobile terminal, such as aterminal device that can perform wireless communication with a basestation or a micro base station, including a mobile phone, a notebook,or the like.

In addition, embodiments of the invention disclosed herein may beimplemented on a computer program product.

More specifically, the computer program product is one of those having acomputer-readable medium encoded with computer program logic, which,when executed on a computing device, provides the associated operationsto achieve the above technical solution of the present invention. Whenexecuted on at least one processor of a computing system, the computerprogram logic causes the processor to perform the operations (methods)described in the embodiments of the present invention. Such anarrangement of the present invention is typically provided as software,codes, and/or other data structures that are arranged or encoded on acomputer-readable medium, such as an optical medium (e.g., a CD-ROM), afloppy disk or a hard disk, or, for example, other media for a firmwareor a microcode on one or more ROM or RAM or PROM chips, or thedownloadable software images, shared database and so on in one or moremodules. Software or firmware or such configuration may be installed ona computing device such that one or more processors in the computingdevice perform the technical solutions described in the embodiments ofthe present invention.

While the present invention has been described in connection with thepreferred embodiments of the present invention, it will be understood bythose skilled in the art that various modifications, substitutions, andalterations may be made therein without departing from the spirit andscope of the invention. Accordingly, the present invention should not belimited by the above-described embodiments, but rather by the appendedclaims and their equivalents.

1.-20. (canceled)
 21. A method performed by a user equipment (UE),comprising: receiving a first RRCConnectionReconfiguration message whichcontains an indication to reconfigure a first data radio bearer (DRB) toa second DRB; and sending a PDCP status report to a base station (eNB),if the UE reconfigures a radio bearer from the first DRB to the secondDRB and if the radio bearer is configured to send the PDCP statusreport, wherein the second DRB is a bearer whose radio protocols arelocated in a base station (eNB) and are not located in a WLAN to use eNBradio resources among the eNB radio resources and WLAN resources, andthe first DRB is a bearer whose radio protocols are located in both theeNB and the WLAN to use both the eNB radio resources and the WLANresources.
 22. The method according to claim 21, further comprising:receiving a second RRCConncctionReconfiguration message which containsan indication to reconfigure the second DRB to the first DRB and adrb-ToAddModList parameter that contains a list of DRBs needed to beadded; reconfiguring a PDCP entity in accordance with a pdcp-Configparameter, if the pdcp-Config parameter is included in thedrb-ToAddModList parameter, wherein the pdcp-Config parameter is used toset configurable PDCP parameters for DRBs; and reconfiguring an RLCentity and/or a DTCH logical channel in accordance with an rlc-Configparameter and a logicalChannelConfig parameter, if the rlc-Configparameter and the logicalChannelConfig parameter are included in thedrb-ToAddModList parameter, wherein the rlc-Config parameter is used tospecify RLC configuration of signaling radio bearers (SRBs) and DRBs,and the logicalChannelConfig parameter is used to configure logicalchannel parameters.
 23. The method according to claim 22, furthercomprising: reconfiguring one adaptation entity for all first DRBs whichreceives data from the PDCP entity.
 24. A method performed by a basestation (eNB), comprising: sending, to a user equipment (UE), a firstRRCConnectionReconfiguration message which contains an indication toreconfigure a first data radio bearer (DRB) to a second DRB; andreceiving a PDCP status report from the UE, if a radio bearer of the UEis reconfigured from the first DRB to the second DRB and if the radiobearer of the UE is configured to send the PDCP status report, whereinthe second DRB is a bearer whose radio protocols are located in the eNBand are not located in a WLAN to use eNB radio resources among the eNBradio resources and WLAN resources, and the first DRB is a bearer whoseradio protocols are located in both the eNB and the WLAN to use both theeNB radio resources and the WLAN resources.
 25. The method according toclaim 24, further comprising: sending, to the UE, a secondRRCConnectionReconfiguration message which contains an indication toreconfigure the second DRB to the first DRB and a drb-ToAddModListparameter that contains a list of DRBs needed to be added, wherein: aPDCP entity of the UE is reconfigured in accordance with a pdcp-Configparameter, if the pdcp-Config parameter is included in thedrb-ToAddModList parameter, wherein the pdcp-Config parameter is used toset configurable PDCP parameters for DRBs; and an RLC entity and/or aDTCH logical channel of the UE are/is reconfigured in accordance with anrlc-Config parameter and a logicalChannelConfig parameter, if therlc-Config parameter and the logicalChannelConfig parameter are includedin the drb-ToAddModList parameter, wherein the rlc-Config parameter isused to specify RLC configuration of signaling radio bearers (SRBs) andDRBs, and the logicalChannelConfig parameter is used to configurelogical channel parameters.
 26. The method according to claim 25,wherein one adaptation entity of the UE for all first DRBs isreconfigured, and the one adaptation entity receives data from the PDCPentity.
 27. A user equipment (UE) comprising: receiving circuitryconfigured to receive a first RRCConnectionReconfiguration message whichcontains an indication to reconfigure a first data radio bearer (DRB) toa second DRB; and transmitting circuitry configured to send a PDCPstatus report to a base station (eNB), if the UE reconfigures a radiobearer from the first DRB to the second DRB and if the radio bearer isconfigured to send the PDCP status report, wherein the second DRB is abearer whose radio protocols are located in a base station (eNB) and arenot located in a WLAN to use eNB radio resources among the eNB radioresources and WLAN resources, and the first DRB is a bearer whose radioprotocols are located in both the eNB and the WLAN to use both the eNBradio resources and the WLAN resources.
 28. The UE according to claim27, wherein the receiving circuitry is further configured to receive asecond RRCConnectionReconfiguration message which contains an indicationto reconfigure the second DRB to the first DRB and a drb-ToAddModListparameter that contains a list of DRBs needed to be added, and the UEfurther comprises: reconfiguring circuitry configured to reconfigure aPDCP entity in accordance with a pdcp-Config parameter, if thepdcp-Config parameter is included in the drb-ToAddModList parameter,wherein the pdcp-Config parameter is used to set configurable PDCPparameters for DRBs, wherein the reconfiguring circuitry is furtherconfigured to reconfigure an RLC entity and/or a DTCH logical channel inaccordance with an rlc-Config parameter and a logicalChannelConfigparameter, if the rlc-Config parameter and the logicalChannelConfigparameter are included in the drb-ToAddModList parameter, wherein therlc-Config parameter is used to specify RLC configuration of signalingradio bearers (SRBs) and DRBs, and the logicalChannelConfig parameter isused to configure logical channel parameters.
 29. The UE according toclaim 28, wherein the reconfiguring circuitry is further configured toreconfigure one adaptation entity for all first DRBs which receives datafrom the PDCP entity.
 30. A base station (eNB) comprising: transmittingcircuitry configured to send, to a user equipment (UE), a firstRRCConnectionReconfiguration message which contains an indication toreconfigure a first data radio bearer (DRB) to a second DRB; andreceiving circuitry configured to receive a PDCP status report from theUE, if a radio bearer of the UE is reconfigured from the first DRB tothe second DRB and if the radio bearer of the UE is configured to sendthe PDCP status report, wherein the second DRB is a bearer whose radioprotocols are located in the eNB and are not located in a WLAN to useeNB radio resources among the eNB radio resources and WLAN resources,and the first DRB is a bearer whose radio protocols are located in boththe eNB and the WLAN to use both the eNB radio resources and the WLANresources.
 31. The eNB according to claim 30, wherein the transmittingcircuitry is further configured to send, to the UE, a secondRRCConnectionReconfiguration message which contains an indication toreconfigure the second DRB to the first DRB and a drb-ToAddModListparameter that contains a list of DRBs needed to be added, wherein: aPDCP entity of the UE is reconfigured in accordance with a pdcp-Configparameter, if the pdcp-Config parameter is included in thedrb-ToAddModList parameter, wherein the pdcp-Config parameter is used toset configurable PDCP parameters for DRBs; and an RLC entity and/or aDTCH logical channel of the UE are/is reconfigured in accordance with anrlc-Config parameter and a logicalChannelConfig parameter, if therlc-Config parameter and the logicalChannelConfig parameter are includedin the drb-ToAddModList parameter, wherein the rlc-Config parameter isused to specify RLC configuration of signaling radio bearers (SRBs) andDRBs, and the logicalChannelConfig parameter is used to configurelogical channel parameters.
 32. The eNB according to claim 31, whereinone adaptation entity of the UE for all first DRBs is reconfigured, andthe one adaptation entity receives data from the PDCP entity.